IS

Ropponen, Janne

Topic Weight Topic Terms
0.174 approach analysis application approaches new used paper methodology simulation traditional techniques systems process based using
0.172 risk risks management associated managing financial appropriate losses expected future literature reduce loss approach alternative
0.126 software development product functionality period upgrade sampling examines extent suggests factors considered useful uncertainty previous

Focal Researcher     Coauthors of Focal Researcher (1st degree)     Coauthors of Coauthors (2nd degree)

Note: click on a node to go to a researcher's profile page. Drag a node to reallocate. Number on the edge is the number of co-authorships.

Lyytinen, Kalle 1 Mathiassen, Lars 1
Content Analysis 1 Information System Failure 1 Risk Management 1 Risk Management Technique 1
Software Development 1 Socio-Technical Analysis 1

Articles (1)

Attention Shaping and Software Risk--A Categorical Analysis of Four Classical Risk Management Approaches. (Information Systems Research, 1998)
Authors: Abstract:
    This paper examines software risk management in a novel way, emphasizing the ways in which managers address software risks through sequential attention shaping and intervention. Software risks are interpreted as incongruent states within a socio-technical model of organizational change that includes task, structure, technology, and actors. Such incongruence can lead to failures in developing or implementing the system and thus to major losses. Based on this model we synthesize a set of software risk factors and risk resolution techniques, which cover the socio-technical components and their interactions. We use the model to analyze how four classical risk management approaches--McFarlan's portfolio approach, Davis' contingency approach, Boehm's software risk approach, and Alter's and Ginzberg's implementation approach--shape managerial attention. This analysis shows that the four approaches differ significantly in their view of the manager's role and possible actions. We advise managers to be aware of the limitations of each approach and to combine them to orchestrate comprehensive risk management practices in a context. Overall, the paper provides a new interpretation of software risk management which goes beyond a narrow system rationalism by suggesting a contingent, contextual, and multivariate view of software development.